Method and device for processing source role information

ABSTRACT

A method and device for processing source role information in which a source role tag is inserted into a packet as an inner VLAN tag of the packet and used to perform role based access control processing for the packet.

BACKGROUND OF THE INVENTION

A user should be verified when accessing a network to guarantee thesecurity of the network, and after the verification is passed, accessrights of the user should be limited by using an access control method,e.g., the access rights of the user are limited by configuring an AccessControl List (ACL). One type of conventional access control method isbased on IP addresses. This has the disadvantage that a large number ofACLs are configured and the configuration and management workload ishigh due to change of IP addresses.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram illustrating a role based access controlstructure in accordance with one example.

FIG. 2 is a schematic diagram illustrating a first application case inaccordance with one example.

FIG. 3 is a schematic diagram illustrating a second application case inaccordance with an example.

FIG. 4 is a schematic diagram illustrating a third application case inaccordance with an example.

FIG. 5 is a schematic diagram illustrating a fourth application case inaccordance with an example.

FIG. 6 is a schematic diagram illustrating a method that an Ingressdevice configures a corresponding relation by using a verification modein accordance with an example.

FIG. 7 is a schematic diagram illustrating a method that an Ingressdevice configures a corresponding relation by using a verification modein accordance with another example.

FIG. 8 is a schematic diagram illustrating a method that an Egressdevice configures a RBACL by using a verification mode in accordancewith an example.

FIG. 9 is a schematic diagram illustrating the structure of an Ingressdevice in accordance with an example.

FIG. 10 is a schematic diagram illustrating the structure of an Ingressdevice in accordance with another example.

FIG. 11 is a schematic diagram illustrating the structure of an Egressdevice in accordance with an example.

FIG. 12 is a schematic diagram illustrating the structure of anintermediate device in accordance with an example.

FIG. 13 is a schematic diagram of a data packet with a source role tag.

FIG. 14 is a schematic diagram of a data packet with a source role tagand an outer VLAN tag.

DETAILED DESCRIPTION

In one example a role based access control method comprises: allocatinga source role tag to a user, allocating a destination role informationto a server, and performing access control processing by configuring anRBACL based on the source role tag and the destination role information.The role based access control method may thought of as combining severalACLs based on different IP addresses into one ACL based on roleinformation including source role information regarding to the user anddestination information regarding to the server. This reduces the numberof ACLs. Moreover, no matter how the IP addresses change, the role tagsdo not change, and thus role based ACL does not change and configurationand management workload is reduced.

An example of a role based access control structure is shown in FIG. 1.User equipment obtains a source role after passing verification, andsource role information is stored in an Ingress device; a resource sidedevice (a server is taken as an example in FIG. 1) obtains a destinationrole after passing verification, and destination role information isstored in an Egress device; a Role Based Access Control List (RBACL) isconfigured. The user equipment transmits a packet to the Ingress device,the Ingress device adds the source role information of the userequipment into the packet and forwards the packet to an intermediatedevice, and the packet always contains the source role informationduring a subsequent forwarding procedure until the packet is forwardedto the Egress device. After receiving the packet, the Egress devicedetermines the destination role information of the packet, matches thesource role information and the destination role information with itemsin the RBACL, and performs access control processing for the packetaccording to a matching result. The access control processing includespermitting forwarding, rejecting forwarding, limiting a forwarding speedand so on. It should be noted that, in the structure shown in FIG. 1,the Ingress device and the Egress device may be configured in a layer-2network or a layer-3 network, a common network device may be configuredbetween the user equipment and the Ingress device or between the Egressdevice and the server, and a middle network device may be configuredbetween the Ingress device and the Egress device.

Various methods have been used to carry source role information in apacket. However, these previous methods have tended to requiresignificant changes to the network hardware. Where such changes areextensive, they can be prohibitively expensive.

A method for processing source role information provided in one examplecomprises: after receiving a packet from user equipment, an Ingressdevice determines a source role tag according to source information ofthe packet, inserts the source role tag into the packet as an innerVirtual Local Area Network (VLAN) tag of the packet, and forwards thepacket, where the source role tag corresponds to a role of the userequipment; if there is an intermediate device between the Ingress deviceand an Egress, the intermediate device keeps the source role tag as theinner VLAN tag unchangeable during a subsequent forwarding procedureuntil the packet is forwarded to the Egress device; the Egress deviceobtains the source role tag as the inner VLAN tag from the packet, andperforms role based access control processing for the packet accordingto the source role tag.

The above method utilizes existing QinQ function of network devices. TheIngress device inserts the source role tag as the inner VLAN tag intothe packet, the intermediate device keeps the source role tag as theinner VLAN tag unchangeable and the Egress device obtains the sourcerole tag as the inner VLAN tag from the packet. Accordingly, thefunctions of conventional devices can be compatible with this method,and do not need to be modified greatly.

The source information of the packet in the above method may include:information of the Ingress device's ingress port receiving the packet,source address information of the packet, a layer-4 port number, layer-3protocol number and application layer protocol number of the packet,etc.

Performing role based access control processing for the packet by theEgress device may include: obtaining the source role tag from thereceived packet, determining destination role information of the packet,matching the source role tag and the destination role information withitems in the RBACL, and performing access control processing for thepacket according to a matching result.

The above method will be described hereinafter in detail with referenceto specific examples. Based on the role based access control structureshown in FIG. 1, there are four application cases.

A first application case: as shown in FIG. 2, user equipment is directlyconnected to an Ingress device, is connected to an intermediate devicethrough a layer-2 network, and then is connected to a layer-3 networkthrough the intermediate device. A server is directly connected to anEgress device, is connected to an intermediate device through a layer-2network, and then is connected to the layer-3 network through theintermediate device. All devices between the Ingress device and theEgress device could be taken as intermediate devices. The Ingress deviceand the Egress device directly interact with an access verificationserver.

A second application case: as shown in FIG. 3, user equipment isconnected to an Ingress device through a common device, is connected toan intermediate device through a layer-2 network, and then is connectedto a layer-3 network through the intermediate device. A server isconnected to an Egress device through a common device, is connected toan intermediate device through a layer-2 network, and then is connectedto the layer-3 network through the intermediate device. All devicesbetween the Ingress device and the Egress device may be taken asintermediate devices. The common devices interact with an accessverification server and transmit source role information of the userequipment passing the verification to the Ingress device.

A third application case: as shown in FIG. 4, different from the firstapplication case, the user equipment and the server are directlyconnected to the Ingress device and the Egress device respectively, andthe Ingress device and the Egress device perform layer-3 forwardingprocessing.

A fourth application case: as shown in FIG. 5, different from the thirdapplication case, the user equipment and the server are connected to theIngress device and the Egress device respectively through commondevices, and the common devices interact with an access verificationserver, and transmit source role information of the user equipmentpassing the verification to the Ingress device.

The common devices in the above application cases are all networkdevices having no tag inserting and processing function.

In the examples of the present invention, the Ingress device stores acorresponding relation between the source information of the packet andthe source role tag, and the Egress device stores the RBACL. Thecorresponding relation between the source information of the packet andthe source role tag and the RBACL may be configured by using a manualconfiguration mode or a verification mode. The verification mode will bedescribed hereinafter in detail.

For the Ingress device, configuring the corresponding relation betweenthe source information of the packet and the source role tag by usingthe verification mode includes: determining the source role informationof the verified user equipment and the source information of the packettransmitted by the verified user equipment, applying the correspondingrelation between the source information of the packet and the sourcerole tag to a hardware plane of the Ingress device. The sourceinformation of the packet includes: the information of the Ingressdevice's ingress port receiving the packet, the source addressinformation of the packet, a layer-4 port number, layer-3 protocolnumber and application layer protocol number of the packet etc.

According to the different application cases, methods for determiningthe source role information of the user equipment passing theverification and the source information of the packet by the Ingressdevice are different, which will be described by taking two examples.

In an example, if the user equipment is directly connected to theIngress device and the Ingress device directly interacts with the accessverification server, which corresponds to the above first and thirdapplication cases, the procedure of configuring by the Ingress devicethe corresponding relation between the source information of the packetand the source role tag by using the verification mode is shown in FIG.6 and includes the following steps.

Step 601, the user equipment initiates a verification request to theIngress device.

Step 602, the Ingress device forwards the verification request to theaccess verification server.

Step 603, the access verification server issues the source roleinformation of the user equipment to the Ingress device after the userequipment passes the verification.

Step 604, the Ingress device applies a corresponding relation betweenthe Ingress device's ingress port receiving the verification request andthe source role tag corresponding to the source role information of theuser equipment to the hardware plane of the Ingress device. Applying bythe Ingress device the corresponding relation between the Ingressdevice's ingress port receiving the verification request and the sourcerole tag corresponding to the role information of the user equipment tothe hardware plane of the Ingress device includes: converting by theIngress device the source role information of the user equipment intothe source role tag, and applying the corresponding relation between theIngress device's ingress port receiving the verification request and thesource role tag to the hardware plane of the Ingress device.

In this example, the Ingress device's ingress port is taken as thesource information of the packet. When the corresponding relation isapplied, the source role tag could be inserted into a field of thereceived packet as an inner VLAN tag at the Ingress device's ingressport. FIG. 13 shows the schematic diagram of the packet having thesource role tag. Since the Ingress device has the QinQ function, theIngress device adds two layers of VLAN fields after receiving the packetthrough the ingress port. The inner VLAN field is the source role tagthat contains the role information of the user equipment, and the outerVLAN field is used for data forwarding. FIG. 14 shows the schematicdiagram of the packet having the source role tag and the outer VLAN tag.

In another example, if the user equipment is connected to the Ingressdevice through a common device and the common device interacts with theaccess verification server, which corresponds to the above second andfourth application cases, the procedure of configuring by the Ingressdevice the corresponding relation between the source information of thepacket and the source role tag by using the verification mode is shownin FIG. 7 and includes the following steps.

Step 701, the user equipment initiates a verification request to thecommon device.

Step 702, the common device forwards the verification request to theaccess verification server.

Step 703, the access verification server issues the source roleinformation of the user equipment to the common device after the userequipment passes the verification.

Step 704, the common device transmits a corresponding relation betweenthe source role information of the user equipment and the source addressinformation of the verification request to the Ingress device.

Step 705, the Ingress device applies the corresponding relation betweenthe source role tag corresponding to the source role information of theuser equipment and the source address information of the verificationrequest of the user equipment to the hardware plane of the Ingressdevice.

In this example, the source address information of the packet is takenas the source information of the packet, and the source addressinformation may be a source IP address or a source MAC address. Afterthe corresponding relation is applied to the hardware plane of theIngress device, the corresponding relation between the source role tagand the source address information (i.e., the source address informationof the verification request of the user equipment) may be stored in ahardware list, and subsequently the Ingress device searches the hardwarelist according to the source address information of the packet todetermine the source role tag.

For the Egress device, configuring the RB CAL by using the verificationmode is shown in FIG. 8 and includes the following steps.

Step 801, the Egress device receives a verification request from aresource side device.

The verification request may be directly transmitted to the Egressdevice by the resource side device or be transmitted to the Egressdevice by the resource side device through a common device. In thisexample, the resource side device is a server.

Step 802, the Egress device forwards the verification request to theaccess verification server.

Step 803, the access verification server issues the destination roleinformation of the resource side device to the Egress device after theresource side device passes the verification.

Step 804, the Egress device applies a corresponding relation between thesource address information of the verification request from the resourceside device and the destination role information of the resource sidedevice to a hardware plane of the Egress device.

The corresponding relation between the source address information of theverification request from the resource side device and the destinationrole information of the resource side device is applied to the hardwareplane of the Egress device, so that the Egress device can search thiscorresponding relation according to the destination address informationof the packet from the user equipment while performing access controlprocesses, to determine a destination role information corresponding todestination address information in the packet from the user equipment,which will be described hereinafter.

In addition, the corresponding relation between the source addressinformation of the verification request from the resource side deviceand the destination role information of the resource side device may bestored in a hardware list, e.g., a layer-2 forwarding list or a layer-3forwarding list, and the destination role information in the hardwarelist does not influence forwarding functions, has unique meaning and isspecial, so as to avoid function interference.

Step 805, the Egress device requests the access verification server fora role based control policy in which the destination role information ofthe resource side device is taken as a destination role.

Step 806, the access verification server issues the role based controlpolicy in which the destination role information of the resource sidedevice is taken as the destination role to the Egress device.

Generally, all role based control policies are configured in the accessverification server in advance, and after receiving the quest in thestep 805, the access verification server issues all role based controlpolicies in which the destination role information of the resource sidedevice is taken as the destination role to the Egress device. Thecontents of each item in the role based control policies include sourcerole information, destination role information and access controlprocessing modes (which include permit, deny, rate limit, mirror,redirect, priority re-mark, statistic and further matching other packetfields).

Step 807, the Egress device converts source role information in the rolebased control policies into the source role tag, obtains a RBACL, andapplies the RBACL to the hardware plane of the Egress device; wherein,each item in the RBACL contains the source role tag, the destinationrole information and the access control processing mode.

Since the changes of the user equipment address information does notaffect the source role information of the user equipment, the sourcerole tag corresponding to the role information of the user equipmentdoes not change. Therefore, the RBACL applied to the hardware plane ofthe Egress device could keep unchangeable due to source role tagcontained in the RBACL. In addition, the RBACL could be applied at theegress port of the Egress device or be applied globally in the EgressDevice.

The access control processing implemented in the hardware plane duringthe packet forwarding procedure will be described hereinafter in detail.

After receiving the packet from the user equipment, the Ingress devicedetermines the source role tag according to the source information ofthe packet, inserts the source role tag into the packet as the innerVLAN tag of the packet and forwards the packet. If the Ingress device islocated in the layer-2 network, the Ingress device performs layer-2forwarding processing for the packet, and if the Ingress device islocated in the layer-3 network, the Ingress device performs layer-3forwarding processing for the packet.

The source role tag inserted into the packet by the Ingress devicecorresponds to the role of the user equipment, and the user equipmentmay be an actual network entity or a logic entity, e.g. an applicationprotocol in a network device. Different roles may be respectivelyconfigured for different application protocols and correspond todifferent source role tags.

Inserting the source role tag into the packet by the Ingress device maybe performed when the Ingress device's ingress port receives the packet,when the Ingress device's egress port forwards the packet, or at anymoment after the packet is received and before the packet is forwarded.The following technical solutions are described by taking an examplethat the source role tag is inserted into the packet when the Ingressdevice's ingress port receives the packet.

According to the above four application cases, a procedure of processingthe packet by the Ingress device will be described hereinafter.

In the first application case shown in FIG. 2, the packet received bythe Ingress device does not contain a tag, and thus is marked as anuntag packet. After receiving the packet, the Ingress device determinesthe source role tag according to the ingress port and the ACL,determines an outer VLAN tag (Vtag), inserts the source role tag as theinner VLAN tag into the packet, and inserts the Vtag into the packet. Ofcause, if there are packets which the source role tag does not need tobe inserted into in the flow of the VLAN of the egress port, e.g.packets are outputted at predetermined port of CPU or no source role tagis configured at the ingress port, the operation of inserting the sourcerole tag is not performed, and only the operation of inserting the Vtagis performed. The above processing is also applied to the followingexamples, and will not be further described.

It should be noted that the Ingress device may determine the source roletag and the Vtag according to the ingress port or according to the ACLconfigured at the ingress port. For example, the items containing thesource role tag corresponding to the source address information orprotocol number of the packet could be configured in the ACL of theingress port in advance, and after receiving the packet, the Ingressdevice may determine the source role tag by matching the items in theACL.

The processing performed by the intermediate device and the Egressdevice is the same as that performed by the Ingress device, and will notbe further described hereinafter. The following technical solutions aredescribed by taking an example that the source role tag and the Vtag aredetermined according to the ingress port.

In addition, the Vtag is used for forwarding the packet, which could belearned from in the prior art and is not modified in the presentinvention. After being determined, the Vtag may be inserted into thepacket or be not inserted into the packet, which is not limited by thepresent invention. The technical solutions of the present invention aredescribed by taking an example of inserting the Vtag into the packet.

The Ingress device searches the layer-2 forwarding list according to theVtag and a destination MAC address of the packet to determine an egressport, and forwards the packet containing the Vtag and source role tagthrough the determined egress port of the Ingress device. If a Vtagstripping function is configured at the egress port of Ingress device,the Ingress device strips the Vtag from the packet firstly, and thenforwards the packet containing the source role tag.

In the second application case shown in FIG. 3, the packet received bythe Ingress device contains the Vtag, the Ingress device searches thecorresponding relation between the source address information of thepacket and the source role tag according to the source addressinformation, determines the source role tag corresponding to the sourceaddress information, and inserts the source role tag as the inner VLANtag into the packet.

The Ingress device searches the layer-2 forwarding list according to theVtag and the destination MAC address of the packet to determine anegress port of the Ingress device, and forwards the packet containingthe Vtag and the source role tag through the determined egress port. Ifa Vtag stripping function is configured at the egress port of theIngress device, the Ingress device strips the Vtag from the packetfirstly, and then forwards the packet containing the source role tag.

In the third application case shown in FIG. 4, the packet received bythe Ingress device is an untag packet. After receiving the packet, theIngress device searches the corresponding relation between the ingressport and the source role tag according to the ingress port, determinesthe source role tag corresponding to the ingress port, determines theVtag corresponding to the ingress port, inserts the source role tag asthe inner VLAN tag of the packet into the packet, and inserts the Vtaginto the packet.

The Ingress device searches the layer-3 forwarding list according to theVtag and a destination IP address of the packet to determine an egressport of the Ingress device, and forwards the packet through thedetermined egress port after performing replacement processing for theVtag, the source MAC address and the destination MAC address. Theforwarded packet contains a new Vtag and the source role tag. If a Vtagstripping function is configured at the egress port, the Ingress devicestrips the new Vtag from the packet firstly, and then forwards thepacket only containing the source role tag.

In the fourth application case shown in FIG. 5, the packet received bythe Ingress device contains the Vtag. The Ingress device searches thecorresponding relation between the source address information of thepacket and the source role tag according to the source addressinformation, determines the source role tag corresponding to the sourceaddress information, and inserts the source role tag as the inner VLANtag of the packet into the packet.

The Ingress device searches the layer-3 forwarding list according to theVtag and the destination IP address of the packet to determine an egressport, and forwards the packet through the determined egress port afterperforming replacement processing for the Vtag, the source MAC addressand the destination MAC address. The forwarded packet contains a newVtag and the source role tag. If a Vtag stripping function is configuredat the egress port, the Ingress device strips the new Vtag from thepacket firstly, and then forwards the packet only containing the sourcerole tag.

In the above processing procedure of the Ingress device, when the sourcerole tag as the inner VLAN tag of the packet is inserted into thepacket, a Tag Protocol Identifier (TPID) of the inner VLAN tag adopts apreset value unequal to 0x8100 to identify the inner VLAN tag as thesource role tag. The TPID of the source role tag could be configuredglobally in the network in which the Ingress Device located.

It should be noted that in some cases (e.g. in a case that the packet isa packet outputted at predetermined port of the CUP or the ingress portis configured not to insert the source role tag into the packet), thesource role tag does not need to be inserted into the received packet;if the packet in this case and the packet containing the source role tagare forwarded through the same egress port, the two packets can keeprespective formats and do not influence with each other.

After receiving the packet, the intermediate device keeps the sourcerole tag as the inner VLAN tag of the packet unchangeable during thelayer-2 or layer-3 forwarding procedure. In other words, if theintermediate device determines that the inner VLAN tag is the sourcerole tag through the TPID of the inner VLAN tag, the intermediate devicekeeps the inner VLAN tag unchangeable.

The layer-2 or layer-3 forwarding processing performed by theintermediate device for the packet is the same as that performed by theIngress device. In the first application case shown in FIG. 2, thepacket received by the intermediate device only contains the source roletag. The intermediate device determines the Vtag corresponding to theintermediate device's ingress port, and inserts the Vtag into thepacket. The intermediate device searches the layer-2 forwarding listaccording to the Vtag and the destination MAC address of the packet todetermine an egress port of the intermediate device, and forwards thepacket through the determined egress port. If a Vtag stripping functionis configured at the egress port of the intermediate device, theintermediate device strips the new Vtag from the packet firstly, andthen forwards the packet only containing the source role tag.

In the second application case shown in FIG. 3, the packet received bythe intermediate device contains the Vtag and the source role tag. Theintermediate device searches the layer-2 forwarding list according tothe Vtag and the destination MAC address of the packet to determine anegress port, and forwards the packet containing the Vtag and the sourcerole tag through the determined egress port. If a Vtag strippingfunction is configured at the egress port, the intermediate devicestrips the Vtag from the packet firstly, and then forwards the packetonly containing the source role tag.

In the third application case shown in FIG. 4, the packet received bythe intermediate device only contains the source role tag. Theintermediate device determines the Vtag corresponding to theintermediate device's ingress port, and inserts the Vtag into thepacket. The intermediate device searches the layer-3 forwarding listaccording to the Vtag and the destination IP address of the packet todetermine an egress port, and forwards the packet through the determinedegress port. The forwarded packet contains the Vtag and the source roletag. If a Vtag stripping function is configured at the determined egressport of intermediate device, the intermediate device strips the new Vtagfrom the packet firstly, and then forwards the packet only containingthe source role tag.

In the fourth application case shown in FIG. 5, the packet received bythe intermediate device contains Vtag and the source role tag. Theintermediate device searches the layer-3 forwarding list according tothe Vtag and the destination IP address of the packet to determine anegress port, and forwards the packet through the determined egress portafter performing replacement processing for the Vtag, the source MACaddress and the destination MAC address. The forwarded packet contains anew Vtag and the source role tag. If a Vtag stripping function isconfigured at the egress port, the intermediate device strips the newVtag from the packet firstly, and then forwards the packet onlycontaining the source role tag.

When receiving the packet forwarded by the intermediate device, theEgress device searches the applied corresponding relation in the step804 shown in FIG. 8, determines destination role informationcorresponding to the destination address (e.g., an destination IPaddress) of the packet, obtains the source role tag as the inner VLANtag from the packet, matches the source role tag and the destinationrole information with items in the RBACL, and performs access controlprocessing for the packet according to a matching result.

In the step 807 shown in FIG. 8, the Egress device applies the RBACL tothe hardware plane, and the RBACL contains the source role tag,destination role information and access control processing modes. Aftermatching the source role tag and the destination role information withthe items in the RBACL, if there is an item which can match with hesource role tag and the destination role information successfully, anaccess control processing mode is determined, e.g. permit, deny, ratelimit, mirror, redirect, priority re-mark, statistic and furthermatching other packet fields.

In addition, the Egress device also performs layer-2 or layer-3forwarding processing inside the Egress device besides the above accesscontrol processing. The processing procedure inside the Egress devicewill be described according to the above four application caseshereinafter in detail.

In the first application case shown in FIG. 2, the packet received bythe Egress device contains the source role tag and the Vtag or onlycontains the source role tag.

If the packet only contains the source role tag, when determining thatthe inner VLAN tag is the source role tag according to the TPID of theinner VLAN tag, the Egress device obtains the source role tag,determines the Vtag according to the Egress device's ingress port, andinserts the Vtag into the packet. The Egress device searches the layer-2forwarding list according to the Vtag and the MAC address to determinean egress port, determines destination role information corresponding tothe destination address of the packet, matches the source role tag andthe destination role information with the items in the RBACL, andperforms access control processing for the packet according to amatching result. For example, if the matching result is permit, theEgress device forwards the packet through the determined egress port ofthe Egress device after stripping both the inner tag and the outer tagof the packet; if the matching result is reject, the Egress device dropsthe packet. When forwarding the packet through the egress port of theEgress device, the Egress device strips the source role tag and theVtag, i.e. the forwarded packet forwarded through the egress port of theEgress device is an untag packet.

The operation of matching the source role tag and the destination roleinformation with the items in the RBACL may be performed before or afterthe operation of searching the layer-2 or layer-3 forwarding list.

If the packet received by the Egress device contains the source role tagand the Vtag, different from the processing for the packet onlycontaining the source role tag, it is not needed to determine the Vtagaccording to the ingress port, and other processing is the same as theprocessing for the packet only containing the source role tag.

In the second application case shown in FIG. 3, the packet forwardingprocess inside the Egress device is the similar to that inside theEgress device in the first application case. However, the Egress devicein FIG. 3 strips the source role tag at the egress port, i.e. the packetforwarded through the egress port of the Egress device contains theVtag.

In the third application case shown in FIG. 4, if the packet received bythe Egress device only contains the source role tag, when determiningthat the inner VLAN tag is the source role tag according to the TPID ofthe inner VLAN tag, the Egress device obtains the source role tag,determines the Vtag according to the ingress port, and inserts the Vtaginto the packet. The Egress device searches the layer-3 forwarding listaccording to the Vtag and the destination IP address to determine theegress port, perform replacement processing for the Vtag, the source MACaddress and the destination MAC address, determines destination roleinformation corresponding to the destination address of the packet,matches the source role tag and the destination role information withthe items in the RBACL, and performs access control processing for thepacket according to the matching result. For example, if the matchingresult is permitting forwarding, the Egress device forwards the packetthrough the determined egress port after stripping all tags of thepacket; if the matching result is rejecting forwarding, the Egressdevice drops the packet. When forwarding the packet through the egressport, the Egress device strips the source role tag and the new Vtag,i.e. the forwarded packet is an untag packet.

If the packet received by the Egress device contains the source role tagand the Vtag, different from the processing for the packet onlycontaining the source role tag, it is not needed to determine the Vtagaccording to the egress port, and other processing is the same as theprocessing for the packet only containing the source role tag.

In the fourth application case shown in FIG. 5, the processing is thesame as that in the third application case, except the Egress devicestrips only the source role tag at the egress port, i.e. the packetforwarded through the egress port contains the new Vtag.

In the above method provided by the examples of the present invention,the processing procedure for the inner VLAN tag and the processingprocedure for the outer VLAN tag do not influence with each other, andafter the source role tag as the inner VLAN tag is inserted, theprocessing performed by the devices for the outer VLAN tag and otherpacket fields is not influenced.

In addition, the above method is described by taking a unicast packet asan example. It should be noted that the processing mode for the sourcerole tag is also applicable to multicast. After the Ingress device, theintermediate device or the Egress device performs layer-2 or layer-3copying for the packet, the copied packet contains the source role tagwhich is the same as a multicast source packet.

The above method may be applied to both a CPU port and a common port ofthe network devices, and the logic processing of the CPU port is thesame as that of the common port.

The forgoing is the detailed description of the method provided by theexamples of the present invention, and the Ingress device, theintermediate device or the Egress device provided by the examples of thepresent invention will be described hereinafter in detail.

FIG. 9 is a schematic diagram illustrating the structure of an Ingressdevice in accordance with an example of the present invention. As shownin FIG. 9, the Ingress device includes a packet receiving unit 901, arole tag determining unit 902, a role tag inserting unit 903 and aforwarding processing unit 904.

The packet receiving unit 901 is configured to receive a packet fromuser equipment.

The role tag determining unit 902 is configured to determine a sourcerole tag according to source information of the packet, where the sourcerole tag corresponds to a role of the user equipment.

The role tag inserting unit 903 is configured to insert the source roletag as an inner VLAN of the packet into the packet.

The forwarding processing unit 904 is configured to forward the packetprocessed by the role tag inserting unit 903.

The packet receiving unit 901, the role tag determining unit 902, therole tag inserting unit 903 and the forwarding processing unit 904 areunits in the hardware plane of the Ingress device, and can beimplemented through a forwarding chip.

In addition, the Ingress device further includes a verificationprocessing unit 911 and a first tag configuring unit 912 to configurerelated information in the hardware plane of the Ingress device.

The verification processing unit 911 is configured to forward averification request from the user equipment to an access verificationserver.

The first tag configuring unit 912 is configured to obtain source roleinformation of the user equipment issued by the access verificationserver, and applies a corresponding relation between the Ingressdevice's ingress port receiving the verification request and the sourcerole tag corresponding to the source role information of the userequipment to the hardware plane of the Ingress device. Specifically, thefirst tag configuring unit 912 converts the source role information ofthe user equipment into the source role tag, and applies thecorresponding relation between the Ingress device's ingress portreceiving the verification request and the source role tag to thehardware plane of the Ingress device.

The role tag determining unit 902 performs, according to thecorresponding relation applied to the hardware plane of the Ingressdevice, an operation of determining the source role tag according to thesource information of the packet. The source information of the packetis the Ingress device's ingress port receiving the packet.

In a different network structure, if there is a common device betweenthe Ingress device and the user equipment and the Ingress deviceinteracts with the access verification server through the common device,the Ingress device may adopt another structure, as shown in FIG. 10. Inthis structure, a role obtaining unit 913 and a second tag configuringunit 914 are used to configure related information in the hardware planeof the Ingress device.

The role obtaining unit 913 is configured to obtain from the commondevice a corresponding relation between the source role information ofthe user equipment and the source address information or protocol numberof the verification request, where the source role information of theuser equipment is issued to the common device by the access verificationserver after the common device forwards the verification request of theuser equipment to the access verification server.

The second tag configuring unit 914 is configured to apply thecorresponding relation between the source role tag corresponding to thesource role information of the user equipment and the source addressinformation or protocol number of the packet to the hardware plane ofthe Ingress device.

The role tag determining unit 902 performs, according to thecorresponding relation applied to the hardware plane of the Ingressdevice, an operation of determining the source role tag according to thesource information of the packet. The source information of the packetis the source address information or protocol number of the packet.

The verification processing unit 911, the first tag configuring unit912, the role obtaining unit 913 and the second tag configuring unit 914are units in the software control plane of the Ingress device.

Specifically, when the role tag inserting unit 903 inserts the sourcerole tag as the inner VLAN tag into the packet, the TPID of the innerVLAN tag is configured as a preset value unequal to 0X8100.

The forwarding processing unit 904 in the Ingress device includes anouter tag inserting sub-unit 941, a forwarding list searching sub-unit942 and an egress port processing sub-unit 943.

The outer tag inserting sub-unit 941 is configured to determine a Vtagof the packet when the packet received by the packet receiving unit 901does not contain the Vtag, and insert the Vtag into the packet.

The forwarding list searching sub-unit 942 is configured to search alayer-2 or layer-3 forwarding list according to the Vtag and destinationaddress information contained in the packet which is received by thepacket receiving unit 901 or according to the Vtag and the destinationaddress information contained in the packet which has been processed bythe outer tag inserting sub-unit 941.

The egress port processing sub-unit 943 is configured to strip or not tostrip the Vtag contained in the packet, and forward the packetcontaining the source role tag through the determined egress port.Whether the Vtag needs to be stripped or not to be stripped depends onthe configuration of the egress port.

When performing layer-3 forwarding, the forward processing unit 904further includes a sub-unit for performing replacement processing forthe Vtag, a source MAC address and a destination MAC address. Since thesub-unit for performing replacement processing is similar to theconventional methods, the sub-unit is not shown in drawings and will notbe further described herein.

The Ingress device may insert the source role tag into the packet whenthe ingress device's ingress port receives the packet, when the ingressdevice's egress port forwards the packet, or at any moment after theingress device's ingress port receives the packet and before the ingressdevice's egress port forwards the packet. The technical solutions shownin FIGS. 9 and 10 are described by taking an example that the sourcerole tag is inserted into the packet when the ingress device's egressport forwards the packet.

FIG. 11 is a schematic diagram illustrating the structure of an Egressdevice in accordance with an example of the present invention. As shownin FIG. 11, the Egress device includes a packet receiving unit 1101, arole tag obtaining unit 1102 and an access control unit 1103.

The packet receiving unit 1101 is configured to receive a packet fromuser equipment.

The role tag obtaining unit 1102 is configured to obtain a source roletag as an inner VLAN tag, where the source role tag corresponds to arole of the user equipment transmitting the packet.

The access control unit 1103 is configured to perform role based accesscontrol processing according to the source role tag.

The packet receiving unit 1101, the role tag obtaining unit 1102 and theaccess control unit 1103 are units in the hardware plane of the Egressdevice, and can be implemented through a forwarding chip.

The access control unit 1103 includes a destination role determiningsub-unit 1131, an access control matching sub-unit 1132 and an accesscontrol processing sub-unit 1133.

The destination role determining sub-unit 1131 is configured todetermine destination role information of the packet.

The access control matching sub-unit 1132 is configured to match thesource role tag and the destination role information with items in theRBACL.

The access control processing sub-unit 1133 is configured to performaccess control processing for the packet according to a matching resultof the access control matching sub-unit 1132.

In addition, the Egress device further includes a verificationprocessing unit 1111, a destination role configuring unit 1112, acontrol list obtaining unit 1113 and a control list configuring unit1114 to configure related information in the hardware plane.

The verification processing unit 1111 is configured to forwards averification request from a resource side device to an accessverification server, and obtain the destination role information of theresource side device issued by the access verification server.

The destination role configuring unit 1112 is configured to apply acorresponding relation between the source address information of theverification request from the resource side device and the destinationrole information of the resource side device to the hardware plane ofthe Egress device.

The control list obtaining unit 1113 is configured to obtain a rolebased control policy, wherein, the role based control policy containsthe source role information, destination role information and accesscontrol mode.

The control list configuring unit 1114 is configured to convert sourcerole information in the role based control policy into the source roletag, obtain a RBACL, and apply the RBACL to the hardware plane of theEgress device, wherein, the each item in the RBACL contains source roletag, destination role information and access control mode.

The destination role determining sub-unit 1131 determines thedestination role information corresponding to the destination address inthe packet from the user equipment according to the correspondingrelation applied to the hardware plane. The access control matchingsub-unit 1132 performs matching processing for the RBACL applied to thehardware plane.

The verification processing unit 1111, the destination role configuringunit 1112, the control list obtaining unit 1113 and the control listconfiguring unit 1114 are units in the software control plane.

The Egress device further includes a forwarding processing unit 1104,and the forwarding processing unit 1104 includes an outer tag insertingsub-unit 1141, a forwarding list searching sub-unit 1142 and an egressprocessing sub-unit 1143.

The outer tag inserting sub-unit 1141 is configured to determine a Vtagof the packet when the packet received by the packet receiving unit 1101does not contain the Vtag, and insert the Vtag as the outer VLAN taginto the packet.

The forwarding list searching sub-unit 1142 is configured to search alayer-2 or layer-3 forwarding list according to the Vtag and thedestination address information contained in the packet which isreceived by the packet receiving unit 1101 or according to the Vtag andthe destination address information contained in the packet which hasbeen processed by the outer tag inserting sub-unit 1141.

The egress processing sub-unit 1143 is configured to strip the sourcerole tag of the packet, and after stripping or not stripping the Vtagcontained in the packet and when the access control unit 1103 determinesto forward the packet, forward the packet through the determined egressport.

In addition, when performing layer-3 forwarding, the forwardingprocessing unit 1104 further includes a unit for performing replacementprocessing for the Vtag, the source MAC address and the destination MACaddress of the packet. Since the sub-unit for performing replacementprocessing belongs to conventional protocols, the sub-unit is not shownin drawings and will not be further described herein.

FIG. 12 is a schematic diagram illustrating the structure of anintermediate device in accordance with an example of the presentinvention. As shown in FIG. 12, the intermediate device includes: apacket receiving unit 1201, a tag identifying unit 1202 and a forwardingprocessing unit 1203.

The packet receiving unit 1201 is configured to receive a packet from anIngress device or another intermediate device.

The tag identifying unit 1202 is configured to identify an inner VLANtag of the packet.

The forwarding processing unit 1203 is configured to keep the inner VLANtag unchangeable when the tag identifying unit 1202 determines duringthe forwarding procedure of the packet that the inner VLAN tag is thesource role tag. The inner VLAN tag corresponds to the role of the userequipment transmitting the packet.

If the tag identifying unit 1202 determines that the TPID of the innerVLAN tag is a preset value unequal to 0X8100, and the tag identifyingunit 1202 determines that the inner VLAN tag is the source role tag.

The forwarding processing unit 1203 includes an outer tag insertingsub-unit 1231, a forwarding list searching sub-unit 1232 and an egressport processing sub-unit 1233.

The outer tag inserting sub-unit 1231 is configured to determine a Vtagof the packet when the packet from the user equipment received by thepacket receiving unit 1201 does not contain the Vtag, and insert theVtag into the packet.

The forwarding list searching sub-unit 1232 is configured to search alayer-2 or layer-3 forwarding list according to the Vtag and thedestination address information contained in the packet which isreceived by the packet receiving unit 1201 or according to the Vtag andthe destination address information contained in the packet which hasbeen processed by the outer tag inserting sub-unit 1231.

The egress port processing sub-unit 1233 is configured to forward thepacket containing the source role tag through the determined egress portafter stripping or not stripping the Vtag contained in the packet.

In addition, when performing layer-3 forwarding, the forwardingprocessing unit 1104 further includes a unit for performing replacementprocessing for the Vtag, the source MAC address and the destination MACaddress of the packet. Since the sub-unit for performing replacementprocessing belongs to conventional protocols, the sub-unit is not shownin drawings and will not be further described herein.

The packet receiving unit 1201, the tag identifying unit 1202 and theforwarding processing unit 1203 are units in the hardware plane of theintermediate device, and can be implemented through a forwarding chip.

It should be noted that all units in the hardware planes of the Ingressdevice, the intermediate device and the Egress device can be integratedin a forwarding chip. When determining to implement the functions of theIngress device, the forwarding chip executes the functions of units inthe hardware plane of the Ingress device; when determining to implementthe functions of the intermediate device, the forwarding chip executesthe functions of units in the hardware plane of the intermediate device;when determining to implement the functions of the Egress device, theforwarding chip executes the functions of units in the hardware plane ofthe Egress device.

The foregoing are only preferred examples of the present invention andare not for use in limiting the protection scope of the presentinvention. Any modification, equivalent replacement and improvement madewithin the scope of the present invention should be covered under theprotection scope of the present invention.

1. A method for processing source role information, applied to a networkcomprising an Ingress device and an Egress device, comprising:receiving, by the Ingress device, a packet from user equipment;receiving, by the Ingress device, source role information of the userequipment after a verification of the user equipment; converting, by theIngress device, the source role information of the user equipment into asource role tag, wherein the source role tag corresponds to a role ofthe user equipment; inserting, by the Ingress device, the source roletag into the packet; and forwarding the packet to the Egress device. 2.The method of claim 1, further comprising: after receiving averification request of the user equipment, forwarding, by the Ingressdevice, the verification request to an access verification server,obtaining the source role information of the user equipment from theaccess verification server to convert the source role information of theuser equipment into the source role tag, and applying a correspondingrelation between the Ingress device's ingress port receiving theverification request and the source role tag to a hardware plane of theIngress device; and determining the source role tag corresponding to theIngress device's ingress port receiving the verification requestaccording to the corresponding relation applied to the hardware plane ofthe Ingress device.
 3. The method of claim 1, further comprising:forwarding, by a common device, a verification request of the userequipment to an access verification server, obtaining source roleinformation of the user equipment issued by the access verificationserver, and transmitting a corresponding relation between the sourcerole information of the user equipment and source address information ofthe verification request to the Ingress device; applying, by the Ingressdevice, the corresponding relation between the source role tagcorresponding to the source role information of the user equipment andthe source address information or a protocol number of the verificationrequest to a hardware plane of the Ingress device; and determining thesource role tag corresponding to the source address information or theprotocol number of the packet according to the corresponding relationapplied to the hardware plane of the Ingress device.
 4. The method ofclaim 1, further comprising: performing, by the Egress device, a rolebased access control processing for the packet based on the source roletag in the packet, wherein performing the role based access controlprocessing for the packet comprises: determining, by the Egress device,destination role information of the packet, matching the source role tagand the destination role information with items in a Role Based AccessControl List (RBACL), and performing access control processing for thepacket according to a matching result.
 5. The method of claim 4, furthercomprising: after receiving a verification request of a resource sidedevice, forwarding, by the Egress device, the verification request tothe access verification server, obtaining destination role informationof the resource side device issued by the access verification server,and applying a corresponding relation between source address informationof the verification request and the destination role information of theresource side device to a hardware plane of the Egress device; obtaininga role based control policy from the access verification server, whereinthe destination role information of the resource side device issued bythe access verification server is taken as destination role information;converting the source role information into the source role tag,obtaining the RBACL, and applying the RBACL to the hardware plane of theEgress device, wherein the RBACL contains source role tag, destinationrole information and access control mode; determining the destinationrole information of the packet from the user equipment comprises:determining the destination role information corresponding todestination address information of the packet from the user equipmentaccording to the corresponding relation applied to the hardware plane ofthe Egress device; and performing, by the Egress device, matchingprocessing according to the RBACL applied to the hardware plane of theEgress device.
 6. The method of claim 1, further comprising: when thesource role tag is taken as an inner VLAN tag, setting a Tag ProtocolIdentity (TPID) of the inner VLAN tag to a preset value unequal to0X8100 to identify the inner VLAN tag as the source role tag; keeping,by an intermediate device connected between the user equipment and theIngress device, the inner VLAN tag unchangeable when determining thatthe TPID of the inner VLAN tag of the packet is the preset value; andobtaining, by the Egress device, the source role tag as the inner VLANtag from the packet when determining that the TPID of the inner VLAN tagof the packet is the preset value.
 7. The method of claim 1, whereinforwarding the packet to the Egress comprises: A1) if the packet doesnot contain an outer VLAN tag (Vtag), determining the Vtag of thepacket, inserting the Vtag into the packet, and performing a step A2);if the packet contains a Vtag, directly performing the step A2); A2)searching a layer-2 or layer-3 forwarding list according to the Vtagcontained in the packet and the destination address information of thepacket to determine an egress port; and A3) forwarding the packetcontaining the source role tag through the determined egress port. 8.The method of claim 1, further comprising: B1) if the packet does notcontain an outer VLAN tag (Vtag(, determining, by the Egress device, theVtag of the packet, inserting the Vtag into the packet, and performing astep B2); if the packet contains a Vtag, directly performing the stepB2); B2) searching a layer-2 or layer-3 forwarding list according to theVtag contained in the packet and the destination address information ofthe packet to determine an egress port; B3) stripping the source roletag of the packet, and forwarding the packet through the determinedegress port when the access control processing indicates to forward thepacket.
 9. An Ingress device, comprising: a packet receiving unit toreceive a packet from user equipment; a role tag determining unit toreceive source role information of the user equipment and convert thesource role information into a source role tag for the packet, whereinthe source role tag corresponds to a role of the user equipment; a roletag inserting unit to insert the source role tag into the packet; and aforwarding processing unit to forward the packet.
 10. The Ingress deviceof claim 9, further comprising a verification processing unit and afirst tag configuring unit; wherein the verification processing unit isto forward a verification request from the user equipment to an accessverification server; the first tag configuring unit is to obtain thesource role information of the user equipment from the accessverification server after a verification of the user equipment, convertthe source role information of the user equipment into the source roletag, and apply a corresponding relation between the Ingress device'singress port receiving the verification request and source role tag to ahardware plane of the Ingress device; and the role tag determining unitis to perform, according to the corresponding relation applied to thehardware plane of the Ingress device, an operation of determining thesource role tag according to the source information of the packet,wherein the source information of the packet includes the Ingressdevice's ingress port receiving the packet.
 11. The Ingress device ofclaim 10, further comprising: a role obtaining unit and a second tagconfiguring unit; wherein the role obtaining unit is to obtain from acommon device a corresponding relation between the source roleinformation of the user equipment and source address information or aprotocol number of the verification request, wherein the source roleinformation of the user equipment is issued to the common device by theaccess verification server after the common device forwards theverification request of the user equipment to the access verificationserver; the second tag configuring unit is to apply the correspondingrelation between the source role tag corresponding to the roleinformation of the user equipment and the source address information orthe protocol number of the packet to the hardware plane of the Ingressdevice; and the role tag determining unit is to perform, according tothe corresponding relation applied to the hardware plane of the Ingressdevice, an operation of determining the source role tag according to thesource information of the packet, wherein the source information of thepacket is the source address information or the protocol number of thepacket.
 12. The Ingress device of claim 9, wherein the role taginserting unit is to insert the source role tag into the packet as aninner VLAN tag of the packet, and set a Tag Protocol Identity (TPID) ofthe inner VLAN tag to a preset value unequal to 0X8100.
 13. The Ingressdevice of claim 9, wherein the forwarding processing unit comprises: anouter tag inserting sub-unit to determine an outer Virtual Local AreaNetwork (VLAN) tag (Vtag) of the packet when the packet received by thepacket receiving unit does not contain the Vtag, and insert the Vtaginto the packet; a forwarding list searching sub-unit to search alayer-2 or layer-3 forwarding list according to the Vtag and destinationaddress information contained in the packet which is received by thepacket receiving unit or according to the Vtag and the destinationaddress information contained in the packet which has been processed bythe outer tag inserting sub-unit; and an egress port processing sub-unitto strip the Vtag contained in the packet, and forward the packetcontaining the source role tag through a determined egress port. 14.-20.(canceled)
 21. A method for processing source role information, appliedto a network comprising an Ingress device and an Egress device,comprising: receiving, by the Egress device, a packet from userequipment via the Ingress device; obtaining, by the Egress device, asource role tag in the packet, wherein the source role tag was insertedinto the packet by the Ingress device after the Ingress device hasconverted source role information of the user equipment into the sourcerole tag; and performing, by the Egress device, a role based accesscontrol processing for the packet based on the source role tag of thepacket.
 22. The method of claim 21, wherein performing the role basedaccess control processing comprises: determining, by the Egress device,destination role information of the packet; matching, by the Egressdevice, the source role tag and the destination role information withitems in a Role Based Access Control List (RBACL); and performing, bythe Egress device, an access control processing for the packet accordingto a result of the matching.
 23. The method of claim 22, furthercomprising: forwarding, by the Egress device, a verification requestfrom a resource side device to an access verification server, andobtaining destination role information of the resource side device fromthe access verification server; applying a corresponding relationbetween source address information of the verification request from theresource side device and the destination role information of theresource side device to a hardware plane of the Egress device; obtaininga role based control policy, wherein the role based control policycontains source role tags, destination role information and accesscontrol mode; converting the source role information into the sourcerole tag, obtaining the RBACL, and applying the RBACL to the hardwareplane of the Egress device, wherein the RBACL contains source role tags,destination role information and access control mode; determining thedestination role information corresponding to a destination address ofthe packet from the user equipment according to the correspondingrelation applied to the hardware plane of the Egress device; andperforming a matching processing for the RBACL applied to the hardwareplane of the Egress device.
 24. The method of claim 21, furthercomprising: determining an outer Virtual Local Area Network (VLAN) tag(Vtag) of the packet in response to a determination that the packet doesnot contain a Vtag; inserting the Vtag into the packet; searching alayer-2 or layer-3 forwarding list according to the Vtag and destinationaddress information contained in the packet; and stripping the sourcerole tag and the Vtag contained in the packet, and forwarding the packetthrough an egress port.
 25. The method of claim 21, wherein the sourcerole information of the user equipment is received from an accessverification server after the user equipment has been verified by theaccess verification server.